Technologies for enhanced credit transactions

ABSTRACT

Technologies for enhancing credit transactions include a point of sale computing system. The point of sale computing system receives payment vehicle data for a credit transaction associated with a purchase event. The point of sale computing system determines whether the credit transaction is an alternate routing candidate. The point of sale computing system routes an authorization request message to an issuer computing system via a payment card network in response to a determination that the credit transaction is not an alternate routing candidate. Alternatively, the point of sale computing system routes the authorization request message directly to the issuer computing system via a PIN debit network in response to a determination that the credit transaction is an alternate routing candidate. A corresponding authorization response message is received by the point of sale computing system via the payment card network or the PIN debit network. Other embodiments are described and claimed.

CROSS REFERENCE TO RELATED APPLICATION

This application claims the benefit of U.S. Provisional PatentApplication Ser. No. 62/129,255, filed on Mar. 6, 2015, entitled SYSTEMSAND METHODS FOR ENHANCED PAYMENT TRANSACTIONS, the disclosure of whichis hereby incorporated by reference in its entirety.

TECHNICAL FIELD

Embodiments of the technologies described herein relate, in general, tothe field of enhancing credit transactions through the leveraging of aprivate communications network, such as a PIN debit network. Moreparticularly, the systems and methods relate to the field of usingout-of-band communication channels to facilitate credit authorizationsand provide enhanced messaging.

BACKGROUND

Merchants can communicate with an acquirer processor in order tofacilitate the merchant accepting a payment card as payment for goods orservices. The electronic communications between the merchant and theacquirer can be restricted to a particular messaging specification orprotocol.

SUMMARY

In an embodiment, the present disclosure is directed, in part, to amethod for enhancing credit transactions. The method includes receiving,by a point of sale computing system, payment vehicle data for a credittransaction associated with a purchase event. The payment vehicle datacan correspond to a payment vehicle tendered for the credit transaction.The method also includes determining, by the point of sale computingsystem, whether the credit transaction is an alternate routing candidatebased at least in part on the payment vehicle data. In response to adetermination that the credit transaction is not an alternate routingcandidate, the method includes transmitting, by the point of salecomputing system, an authorization request message for the credittransaction to an issuer computing system via a first communicationschannel and receiving, by the point of sale computing system, anauthorization response message from the issuer computing system via thefirst communications channel. The issuer computing system is associatedwith the payment vehicle tendered for the credit transaction.Additionally, in response to a determination that the credit transactionis an alternate routing candidate, the method includes transmitting, bythe point of sale computing system, the authorization request messagefor the credit transaction to the issuer computing system via a secondcommunications channel different from the first communications channel,receiving, by the point of sale computing system, the authorizationresponse message from the issuer computing system via the secondcommunications channel, and finalizing, by the point of sale computingsystem, the credit transaction associated with the purchase event basedon the authorization response message.

In another embodiment, the present disclosure is directed, in part, to asystem for enhanced credit transactions. The system includes a point ofsale computing device having a processor executing instructions storedin memory. The instructions, when executed, cause the processor toreceive payment vehicle data for a credit transaction associated with apurchase event. The payment vehicle data corresponds to a paymentvehicle tendered for the credit transaction. The instructions furthercause the processor of the point of sale computing device to determinewhether the credit transaction is an alternate routing candidate basedat least in part on the payment vehicle data. In response to adetermination that the credit transaction is not an alternate routingcandidate, the instructions cause the processor of the point of salecomputing device to transmit an authorization request message for thecredit transaction to an issuer computing device via a firstcommunications channel and receive an authorization response messagefrom the issuer computing device via the first communications channel.The issuer computing device is associated with the payment vehicletendered for the credit transaction. Additionally, in response to adetermination that the credit transaction is an alternate routingcandidate, the instructions cause the processor of the point of salecomputing device to transmit the authorization request message for thecredit transaction to the issuer computing device via a secondcommunications channel different from the first communications channel,receive the authorization response message from the issuer computingdevice via the second communications channel; and finalize the credittransaction associated with the purchase event based on theauthorization response message.

In another embodiment, the present disclosure is directed, in part, to amethod for enhancing credit transactions. The method includesdetermining, by an issuer computing system, whether an authorizationrequest message received from a point of sale computing device isreceived via a first communications channel or a second communicationschannel. The authorization request message corresponds to a credittransaction associated with a purchase event and the firstcommunications channel is different from the second communicationschannel. In response to a determination that the authorization requestmessage is received from the point of sale computing device via thefirst communications channel, the method includes generating, by theissuer computing system, an authorization response message for thecredit transaction based at least in part on the authorization requestmessage received from the point of sale computing system via the firstcommunications channel and transmitting, by issuer computing system, theauthorization response message for the credit transaction to the pointof sale computing device via the first communications channel.Additionally, in response to a determination that the authorizationrequest message is received from the point of sale computing device viathe second communications channel, the method includes generating, bythe issuer computing system, an authorization response message for thecredit transaction based at least in part on the authorization requestmessage received from the point of sale computing system via the secondcommunications channel and transmitting, by issuer computing system, theauthorization response message for the credit transaction to the pointof sale computing device via the second communications channel.

In another embodiment, the present disclosure is directed, in part, to asystem for enhanced credit transactions. The system includes an issuercomputing device having a processor executing instructions stored inmemory. The instructions, when executed, cause the processor todetermine whether an authorization request message received from a pointof sale computing device is received via a first communications channelor a second communications channel. The authorization request messagecorresponds to a credit transaction associated with a purchase event andthe first communications channel is different from the secondcommunications channel. In response to a determination that theauthorization request message is received from the point of salecomputing device via the first communications channel, the instructionscause the processor of the issuer computing device to generate anauthorization response message for the credit transaction based at leastin part on the authorization request message received from the point ofsale computing device via the first communications channel and transmitthe authorization response message for the credit transaction to thepoint of sale computing device via the first communications channel.Additionally, in response to a determination that the authorizationrequest message is received from the point of sale computing device viathe second communications channel, the instructions cause the processorof the issuer computing device to generate an authorization responsemessage for the credit transaction based at least in part on theauthorization request message received from the point of sale computingdevice via the second communications channel and transmit theauthorization response message for the credit transaction to the pointof sale computing device via the second communications channel.

BRIEF DESCRIPTION OF THE DRAWINGS

It is believed that certain embodiments will be better understood fromthe following description taken in conjunction with the accompanyingdrawings, in which like references indicate similar elements and inwhich:

FIG. 1 is a simplified block diagram of at least one embodiment of asystem for leveraging a PIN debit network to provide enhanced creditprocessing and messaging;

FIG. 2 is a simplified messaging and processing flow diagram of at leastone embodiment of the system of FIG. 1 for providing enhanced credittransaction functionality;

FIG. 3 is a simplified flow diagram of at least one embodiment of amethod that may be executed by the point of sale computing system ofFIGS. 1 and 2 for leveraging a PIN debit network to provide enhancedcredit processing and messaging;

FIG. 4 is a simplified flow diagram of at least one embodiment of amethod that may be executed by the issuer computing system of FIGS. 1and 2 for leveraging a PIN debit network to provide enhanced creditprocessing and messaging;

FIG. 5 is a simplified messaging and processing flow diagram of at leastone other embodiment of the system of FIG. 1 for providing enhancedcredit transaction functionality;

FIG. 6 is a simplified flow diagram of at least one other embodiment ofa method that may be executed by the point of sale computing system ofFIGS. 1 and 5 for leveraging a PIN debit network and a card network toprovide enhanced credit processing and messaging;

FIG. 7 is a simplified flow diagram of at least one embodiment of amethod that may be executed by the issuer computing system of FIGS. 1and 5 for leveraging a PIN debit network and a card network to provideenhanced credit processing and messaging; and

FIG. 8 is a simplified block diagram of at least one embodiment of asystem for leveraging a PIN debit network and a card network to providecredit processing and messaging.

DETAILED DESCRIPTION

Various non-limiting embodiments of the present disclosure will now bedescribed to provide an overall understanding of the principles of thestructure, function, and use of systems and methods disclosed herein.One or more examples of these non-limiting embodiments are illustratedin the selected examples disclosed and described in detail withreference made to the figures in the accompanying drawings. Those ofordinary skill in the art will understand that systems and methodsspecifically described herein and illustrated in the accompanyingdrawings are non-limiting embodiments. The features illustrated ordescribed in connection with one non-limiting embodiment can be combinedwith the features of other non-limiting embodiments. Such modificationsand variations are intended to be included within the scope of thepresent disclosure.

For simplicity, the description that follows will be provided byreference to a “payment vehicle” or a “payment card,” which generallyrefers to any type of financial alternative to currency. As is to beclear to those skilled in the art, no aspect of the present disclosureis specifically limited to a specific type of payment vehicle or paymentcard. Therefore, it is intended that the following descriptionencompasses the use of the present disclosure with many other forms offinancial alternatives to currency, including credit cards, debit cards,smart cards, chip-based payment cards, single-use cards, prepaid cards,electronic currency (such as might be provided through a cellulartelephone or personal digital assistant), and the like. Payment vehiclesor payment cards can be traditional plastic transaction cards,titanium-containing, or other metal-containing, transaction cards, clearand/or translucent transaction cards, foldable or otherwiseunconventionally-sized transaction cards, radio-frequency enabledtransaction cards, or other types of transaction cards, such as credit,charge, debit, prepaid or stored-value cards, electronic benefittransfer cards, a “virtual” card (e.g., in the form of a display on asmart phone), or any other like financial transaction instrument. In anyevent, the payment vehicles described herein communicate accountinformation (e.g., an account number or other account indicativeinformation) during a purchase event and/or payment or credittransaction.

As is known in the art, merchants typically communicate with an acquirerprocessor (sometimes called a merchant processor or a merchant acquirer)in order to facilitate the merchant accepting a payment card as paymentfor goods or services. The electronic communications between themerchant and the acquirer are generally restricted to a particularmessaging specification or protocol, thereby limiting the opportunity toprovide enhanced messaging using that communication stream. As such,there exists a need for alternative payment systems and methods thatallow merchants, consumers, and/or other entities, such as card issuers,to enjoy enhanced payment and credit transaction experiences. Inaccordance with the present disclosure, a PIN debit network or othertype of private communications network can allow for additionalmessaging between the merchant and the issuer or between the merchantand the acquirer. The PIN debit network and other private communicationsnetworks of the present disclosure can be pre-existing, closed-loopcommunication channels connecting a point of sale (POS) computing systemof a merchant to a third party, such as an acquirer computing system ofan acquirer, an issuer computing system of an issuer financialinstitution, and any other entity or computing device. ConventionalPIN-based transactions are routed through a PIN debit network instead ofa card network operated by a card brand, such as VISA or MASTERCARD. Insome configurations, the PIN debit network is a one-to-many network,connecting a plurality of POS computing systems to a single acquirercomputing system, issuer computing system, or other computing device orconnecting a single POS computing system to multiple computing devices(e.g., acquirer computing system(s), issuer financial institution(s),redemption platform operator(s), etc.). Additionally, in someembodiments, the PIN debit network is a many-to-many network connectinga plurality of POS devices to multiple computing devices. In accordancewith the present disclosure, these pre-existing communications channelscan be configured to facilitate the enhanced messaging and processingdescribed herein. By utilizing pre-existing communications channels(such as a PIN debit network) integration efforts needed to implementthe technologies described herein can be reduced.

Referring now to FIG. 1, in one embodiment, a system 100 for providingenhanced credit processing and messaging includes a merchant 110, anacquirer 130, an issuer financial institution 140, a PIN debit network150, and one or more card networks 160. As described in more detailbelow, the PIN debit network 150 can be leveraged as an out-of-bandcommunications network configured to support enhanced payment or credittransaction messaging between a point of sale (POS) computing system 112of the merchant 110 and an issuer computing system 142 of the issuerfinancial institution 140. In doing so, it should be appreciated thatthe PIN debit network 150 can be configured to capture, bundle, andcommunicate various types of data (e.g., financing offer data, creditline increase offer or request data, balance transfer offer or request,discount offer data, new account offer or request data, interest rateacknowledgement data, electronic terms and conditions acceptance data,new account application data, etc.) between payment devices and systemsthat cannot otherwise be communicated over traditional payment cardnetworks 160 due to strict financial transaction messagingspecifications (e.g., ISO 8583, etc.) and/or protocol requirements.

In an embodiment, the POS computing system 112 receives payment vehicledata associated with a payment vehicle 104 tendered by a consumer 102for a credit transaction. The credit transaction can correspond to thepurchase of goods or services (e.g., a purchase event) by the consumer102. Based on the payment vehicle data and/or other transaction-specificparameters, the POS computing system 112 determines whether to directlyroute an authorization request message for the credit transaction to theissuer computing system 142 via the PIN debit network 150 or whether toroute the authorization request message to the issuer computing system142 via the card network(s) 160 (and any intermediary computing systemssuch as the acquirer computing system 132) using traditional creditprocessing techniques and messaging. In embodiments in which theauthorization request message is directly routed to the issuer computingsystem 142 via the PIN debit network 150, the POS computing system 112can utilize the PIN debit network 150 to communicate additional types ofdata that could not otherwise be communicated via the card network(s)160 due to strict financial transaction messaging specifications andprotocols. In that way, the PIN debit network 150 can be configured toprovide a flexible and bi-directional communications channel between thePOS computing system 112 and the issuer computing system 142 (and anyother computing device communicatively coupled thereto).

Upon receipt of the authorization request message, the issuer computingsystem 142 can generate an authorization response message, which can bedirectly transmitted to the POS computing system 112 via the PIN debitnetwork 150. The POS computing system 112 can finalize the credittransaction based at least in part on, or otherwise as a function of,the received authorization response message. In some embodiments, uponreceipt of the authorization request message and prior to generation ofthe authorization response message, the issuer computing system 142 canbe configured to request additional data from the consumer 102 via thePIN debit network 150 and the POS computing system 112. As discussedherein, such additional data can correspond to an offer related to thecredit transaction and/or an account of the consumer 102. In suchembodiments, the issuer computing system 142 can be configured togenerate a response request message, which can be directly transmittedto the POS computing system 112 via the PIN debit network 150. Theissuer computing system 142 can be configured to receive response datafrom the POS computing system 112 via the PIN debit network 150. Thereceived response data can be based on the response request messagetransmitted to the POS computing system 112. In some embodiments, theresponse data can be elicited from the consumer 102 via the POScomputing system 112 (or a computing or input device associatedtherewith). It should be appreciated that such response data (e.g.,additional or non-conforming transaction data, consumer data, loyaltydata, offer data, account data, SKU data, etc.) cannot be transmittedvia the card network(s) 160 due to the strict financial transactionmessaging specifications and protocols employed. Subsequently, theissuer computing system 142 can generate the authorization responsemessage based at least in part on the received response data.

In other illustrative embodiments, the POS computing system 112 receivespayment vehicle data associated with a payment vehicle 104 tendered by aconsumer 102 for a credit transaction. In such embodiments, the POScomputing system 112 transmits an authorization request message for thecredit transaction to the issuer computing system 142 via the cardnetwork(s) 160. Additionally, the POS computing system 112 transmits anenhanced data message to the issuer computing system 142 via the PINdebit network 150. The enhanced data message includes additional typesof data (e.g., additional transaction data, non-conforming transactiondata, consumer data, loyalty data, offer data, account data, SKU data,etc.) that cannot otherwise be communicated via the card network(s) 160due to the strict financial transaction messaging specifications andprotocols employed. In that way, the PIN debit network 150 can beconfigured to provide a flexible and bi-directional communicationschannel between the POS computing system 112 and the issuer computingsystem 142 (and any other computing device communicatively coupledthereto).

The issuer computing system 142 can be configured to match theauthorization request message received from the POS computing system 112via the card network(s) 160 with the enhanced data message received fromthe POS computing system 112 via the PIN debit network 150. In someembodiments, after matching the authorization request message with theenhanced data message, the issuer computing system 142 can be configuredto generate an authorization response message, which can be transmittedto the POS computing system 112 via the card network(s) 160 and anyintermediary devices (e.g., the acquirer computing system 132, etc.).The POS computing system 112 can be configured to finalize the credittransaction based on the received authorization response message.

In other embodiments, after matching the authorization request messagewith the enhanced data message, the issuer computing system 142 can beconfigured to determine whether a response from the consumer 102 isrequired as part of the credit transaction. In such embodiments, theissuer computing system 142 can transmit a response request message tothe POS computing system 112 via the PIN debit network 150.Subsequently, the issuer computing system 142 can process response datareceived from the POS computing system 112 via the PIN debit network150. Thereafter, the issuer computing system 142 can be configured togenerate an authorization response message, which can be based on theenhanced data message and the response data received from the POScomputing system 112. The authorization response message can betransmitted to the POS computing system 112 via the card network(s) 160for finalization of the credit transaction.

The consumer 102, sometimes referred to as a cardholder, bankcardholder, or card member, can provide information from a paymentvehicle 104 to the POS computing system 112 to initiate a payment orcredit transaction with the merchant 110. The payment or credittransaction can correspond to a purchase event. As discussed, thepayment vehicle 104 can be embodied as any type of physical or virtualpayment vehicle having account information (e.g., an account number orother account indicative information) associated therewith.

The merchant 110 can be embodied as any type of retailer, serviceprovider, vendor, or any other type of entity that sells, or offers tosell, a good and/or service. To facilitate sales and accountingactivities, the merchant 110 can include various communication networksand computing devices (e.g., sales terminals, back-end servers, paymententry devices, card readers, mobile devices, etc.). For example, asillustratively shown, the merchant 110 includes the POS computing system112. Of course, the merchant 110 can include other computing devices orarchitectures commonly used by retail merchants, which are notillustrated in FIG. 1 for clarity of the description. In someembodiments such as the one shown in FIG. 1, the merchant 110 (orcomputing devices thereof) can be in networked communication with theacquirer computing system 132 and use the payment/credit processingservices of the acquirer computing system 132. Payment/credit processingservices can include receiving and responding to authorization requestsas well as facilitating the settlement of funds associated withpayment/credit card-based transactions occurring at the merchant 110.

The POS computing system 112 can be embodied as a computing device orserver capable of processing, communicating, storing, maintaining, andtransferring data. For example, the POS computing system 112 can beembodied as a server, a microcomputer, a minicomputer, a mainframe, adesktop computer, a laptop computer, a mobile computing device, ahandheld computer, a smart phone, a tablet computer, a personal digitalassistant, a telephony device, a custom chip, an embedded processingdevice, or other computing device and/or suitable programmable device.In some embodiments, the POS computing system 112 can be embodied as acomputing device integrated with other systems or subsystems. In theillustrative embodiment of FIG. 1, the POS computing system 112 includesa processor 114, a system bus 116, a memory 118, a data storage 120,communication circuitry 122, and one or more peripheral devices 124. Ofcourse, the POS computing system 112 can include other or additionalcomponents, such as those commonly found in a server and/or computer(e.g., various input/output devices), in other embodiments.Additionally, in some embodiments, one or more of the illustrativecomponents can be incorporated in, or otherwise from a portion of,another component. For example, the memory 118, or portions thereof, canbe incorporated in the processor 114 in some embodiments. Furthermore,it should be appreciated that the POS computing system 112 can includeother components, sub-components, and devices commonly found in acomputer and/or computing device, which are not illustrated in FIG. 1for clarity of the description.

The processor 114 can be embodied as any type of processor capable ofperforming the functions described herein. For example, the processor114 can be embodied as a single or multi-core processor, a digitalsignal processor, microcontroller, a general purpose central processingunit (CPU), a reduced instruction set computer (RISC) processor, aprocessor having a pipeline, a complex instruction set computer (CISC)processor, an application specific integrated circuit (ASIC), aprogrammable logic device (PLD), a field programmable gate array (FPGA),or other processor or processing/controlling circuit or controller.

In various configurations, the POS computing system 112 includes asystem bus 116 for interconnecting the various components of the POScomputing system 112. The system bus 116 can be embodied as, orotherwise include, memory controller hubs, input/output control hubs,firmware devices, communication links (e.g., point-to-point links, buslinks, wires, cables, light guides, printed circuit board traces, etc.)and/or other components and subsystems to facilitate the input/outputoperations with the processor 114, the memory 118, and other componentsof the POS computing system 112. In some embodiments, the POS computingsystem 112 can be integrated into one or more chips such as aprogrammable logic device or an application specific integrated circuit(ASIC). In such embodiments, the system bus 116 can form a portion of asystem-on-a-chip (SoC) and be incorporated, along with the processor114, the memory 118, and other components of the POS computing system112, on a single integrated circuit chip.

The memory 118 can be embodied as any type of volatile or non-volatilememory or data storage capable of performing the functions describedherein. For example, the memory 118 can be embodied as read only memory(ROM), random access memory (RAM), cache memory associated with theprocessor 114, or other memories such as dynamic RAM (DRAM), static RAM(SRAM), programmable ROM (PROM), electrically erasable PROM (EEPROM),flash memory, a removable memory card or disk, a solid state drive, andso forth. In operation, the memory 118 can store various data andsoftware used during operation of the POS computing system 112 such asoperating systems, applications, programs, libraries, and drivers.

The data storage 120 can be embodied as any type of device or devicesconfigured for short-term or long-term storage of data such as, forexample, memory devices and circuits, memory cards, hard disk drives,solid-state drives, or other data storage devices. For example, in someembodiments, the data storage 120 includes storage media such as astorage device that can be configured to have multiple modules, such asmagnetic disk drives, floppy drives, tape drives, hard drives, opticaldrives and media, magneto-optical drives and media, Compact Disc (CD)drives, Compact Disc Read Only Memory (CD-ROM), Compact Disc Recordable(CD-R), Compact Disc Rewriteable (CD-RW), a suitable type of DigitalVersatile Disc (DVD) or Blu-Ray disc, and so forth. Storage media suchas flash drives, solid state hard drives, redundant array of individualdisks (RAID), virtual drives, networked drives and other memory meansincluding storage media on the processor 114, or the memory 118 are alsocontemplated as storage devices. It should be appreciated that suchmemory can be internal or external with respect to operation of thedisclosed embodiments. It should also be appreciated that certainportions of the processes described herein can be performed usinginstructions stored on a computer-readable medium or media that director otherwise instruct a computer system to perform the process steps.Non-transitory computer-readable media, as used herein, comprises allcomputer-readable media except for transitory, propagating signals.

The communication circuitry 122 of the POS computing system 112 can beembodied as any type of communication circuit, device, interface, orcollection thereof, capable of enabling communications between the POScomputing system 112 (or other computing devices associated with amerchant 110) and the acquirer computing system 132 (or other computingdevices of an acquirer 130), the PIN debit network 150 (or computingdevices associated therewith), the card network(s) 160 (or computingdevices associated therewith), the issuer computing system 142 (or othercomputing devices of an issuer financial institution 140), and/or anyother computing device communicatively coupled thereto. For example, thecommunication circuitry 122 can be embodied as one or more networkinterface controllers (NICs), in some embodiments. The communicationcircuitry 122 can be configured to use any one or more communicationtechnologies (e.g., wireless or wired communications) and associatedprotocols (e.g., Ethernet, WiMAX, etc.) to effect such communication.

In some embodiments, the POS computing system 112 (or other computingdevices associated with the merchant 110), the acquirer computing system132 (or other computing devices of the acquirer 130), the PIN debitnetwork 150 (or computing devices associated therewith), the cardnetwork(s) 160 (or computing devices associated therewith), the issuercomputing system 142 (or other computing devices of the issuer financialinstitution 140), and/or any other computing devices of the system 100,can communicate with each other over one or more networks. Thenetwork(s) can be embodied as any number of various wired and/orwireless communication networks. For example, the network(s) can beembodied as or otherwise include a local area network (LAN), a wide areanetwork (WAN), a cellular network, or a publicly-accessible, globalnetwork such as the Internet. Additionally, the network(s) can includeany number of additional devices to facilitate communications betweenthe computing devices of the system 100.

Additionally, in some embodiments, the POS computing system 112 canfurther include one or more peripheral devices 124. Such peripheraldevices 124 can include any type of peripheral device commonly found ina computing device such as additional data storage, speakers, a hardwarekeyboard, a keypad, a gesture or graphical input device, a motion inputdevice, a touchscreen interface, one or more displays, an audio unit, avoice recognition unit, a vibratory device, a computer mouse, aperipheral communication device, and any other suitable user interface,input/output device, and/or other peripheral device.

In some embodiments, the POS computing system 112 can include a cardreader or a PIN pad configured to facilitate receipt of a paymentvehicle 104 or a payment card for a purchase or payment transaction(e.g., a credit or debit transaction). The POS computing system 112 canbe configured to perform certain business-related functions, such as,without limitation, sales tabulation, inventory management, scheduling,accounting processes, payroll, and the like. Additionally, in someembodiments, the POS computing system 112 can include payment hardwareand functionality configured for receiving traditional payment cardscontaining magnetic stripes (e.g., magstripes, swipe cards, etc.). ThePOS computing system 112 can also include payment hardware andfunctionality configured for receiving payment cards via Near FieldCommunication (NFC) technologies, BLUETOOTH communication technologies,and other contactless and/or short-range wireless communicationtechnologies. Additionally or alternatively, in some embodiments, thePOS computing system 112 can include integrated circuit payment hardwareand functionality configured for receiving a EUROPAY, MASTERCARD, ANDVISA (EMV) payment card or other smartcard or chip-based card. The POScomputing system 112 can include any other type of payment hardware andfunctionality for receiving a payment card or vehicle. As used herein,the term POS computing system 112 is used broadly to include POS systemsat brick-and-mortar locations and “virtual” POS systems and devices thatcan be associated with an online retailer, “in-app” purchases, or othertypes of card not present (CNP) transactions.

The POS computing system 112 can facilitate the transmission oftransaction-related information to the acquirer computing system 132, asis known in the art. The transaction-related information can comprise anauthorization request as well as other types of identifying indicia. Theidentifying indicia can vary based on the POS computing system 112, thetype of merchant 110, and the type of transaction, but example types ofidentifying indicia can include any of the following: a merchantidentification number (MID) identifier; a loyalty program identifier; abank identification number (BIN) or other bank identifier associatedwith the payment vehicle 104 tendered in the payment/credit transactioncorresponding to the purchase event; an account identifier associatedwith the payment vehicle 104 tendered in the payment/credit transactioncorresponding to the purchase event; a merchant category code (MCC)identifier; a media access control (MAC) identifier; an InternetProtocol (IP) identifier; a geographic identifier; a payment typeidentifier; a consumer identifier (e.g., a consumer name, a consumeraddress, a consumer phone number, a consumer email address, a uniqueconsumer number, etc.) associated with a consumer 102 engaged in thepurchase event; and/or a cardholder identifier (e.g., a cardholder name,a cardholder address, a cardholder phone number, a cardholder emailaddress, a unique cardholder number, etc.) associated with the paymentvehicle 104 tendered in the credit/payment transaction corresponding tothe purchase event.

In the illustrative embodiment, the POS computing system 112communicates with the issuer computing system 142 (or other computingdevices associated with the issuer financial institution 140) over thePIN debit network 150. The PIN debit network 150 is generally a type ofa private communications network that governs and processes purchase andpayment transactions where the consumer is validated through thecombination of presentment of a plastic card and entry of a PIN orsignature. Typical debit payment brand networks include STAR, PULSE,MAESTRO USA, JEANIE and INTERLINK. The PIN debit network 150 can be anestablished or pre-existing communication channel between the POScomputing system 112 and a third party, such as, for example, the issuercomputing system 142 of the issuer financial institution 140, theacquirer computing system 132 of the acquirer 130, and/or any otherentity or computing device.

As described herein, the PIN debit network 150 can be used as a privatecommunications network directly or indirectly connecting a merchant 110to the issuer financial institution 140 and/or other entities. Unliketraditional payment or card networks 160 that often have regimentedtransaction messaging specifications and protocols, the PIN debitnetwork 150 can offer flexibility with regard to the messaging formatand content, thereby allowing a merchant 110, issuer financialinstitution 140, or other entity to offer enhanced features to a varietyof stakeholders. In that way, the PIN debit network 150 is embodied as acommunications network out-of-band from the card network(s) 160.

The acquirer computing system 132 of the acquirer 130 can be embodied asany type of computing or payment device capable of performing thefunctions described herein. As such, the acquirer computing system 132can include devices and structures commonly found in computing devicessuch as processors, memory devices, communication circuitry, and datastorages, which are not shown in FIG. 1 for clarity of the description.In the illustrative embodiments, the acquirer computing system 132communicates with the issuer computing system 142 (or other computingdevices associated with the financial institution 140) over the one ormore payment or card networks 160. The card network(s) 160 can be, forexample, a network of a credit card association affiliated with apayment vehicle or payment card. Non-limiting examples of credit cardassociations include VISA, MASTERCARD, DISCOVER, and AMERICAN EXPRESS.In some embodiments, the card network(s) 160 receive an authorizationrequest message from the acquirer computing system 132 for a credit orpayment transaction. The card network(s) 160 can provide theauthorization request message to a payment processing server of anissuer processor (not shown), which in turn can provide theauthorization request message to the issuer computing system 142 (orother computing device) of the issuer financial institution 140. Theissuer financial institution 140 (via the issuer computing system 142 orother computing device) can then associate the payment vehicle 104 orpayment card used with an account held by the issuer financialinstitution 140. Thereafter, the issuer financial institution 140 cantransmit an authorization response message to the card network(s) 160via the issuer processor. In response to receiving the authorizationresponse message, the card network(s) 160 can transmit the authorizationresponse message to the acquirer computing system 132. In someembodiments, the card network(s) 160 include a payment gateway (notshown) configured to facilitate the acquirer computing system 132 or,more generally, merchants 110 in processing payment and purchasetransactions.

The issuer computing system 142 of the issuer financial institution 140can be embodied as any type of computing device capable of performingthe functions described herein. As such, the issuer computing system 142can include devices and structures commonly found in computing devicessuch as processors, memory devices, communication circuitry, and datastorages, which are not shown in FIG. 1 for clarity of the description.In the illustrative embodiment, the issuer computing system 142 receivesauthorization request messaging (e.g., credit or payment authorizationrequest messages) either directly from the POS computing system 112 viathe PIN debit network 150 or indirectly from the POS computing system112 via the acquirer computing system 132 and the card network(s) 160.The issuer computing system 142 is also configured to generate andtransmit an authorization response message either directly to the POScomputing system 112 via the PIN debit network 150 or indirectly to thePOS computing system 112 via the acquirer computing system 132 and thecard network(s) 160. As described in more detail below, the issuercomputing system 142 is also configured to bi-directionally communicatewith the POS computing system 112 via the PIN debit network 150. Forexample, the issuer computing system 142 can be configured to providespecial financing offers to the consumer 102 via direct communicationswith the POS computing system 112. The issuer computing system 142 canalso be configured to electronically accept new account applicationsfrom the consumer 102 via direct communications with the POS computingsystem 112. In another example, the issuer computing system 142 isconfigured to electronically interact with the consumer 102 via the POScomputing system 112 to offer and/or approve credit line increases. Itshould be appreciated that such types of data and messaging cannot becommunicated over traditional payment card networks 160 due to strictfinancial transaction messaging specifications (e.g., ISO 8583, etc.)and/or protocol requirements employed.

In some embodiments, the POS computing system 112 (or other computingdevices of the merchant 110), the PIN debit network 150 (or computingdevices thereof), the card network(s) 160 (or computing devicesthereof), the acquirer computing system 132 (or other computing devicesof the acquirer 130), and the issuer computing system 142 (or othercomputing devices of the issuer financial institution 140) can eachestablish an environment during operation. Each environment can includevarious modules, components, sub-components, and devices commonly foundin computing devices, which are not illustrated in the figures forclarity of the description. The various modules, components,sub-components, and devices of each environment can be embodied ashardware, firmware, software, or a combination thereof. For example, oneor more of the modules, components, sub-components, and devices of eachenvironment can be embodied as a processor and/or a controllerconfigured to provide the functionality described herein.

Referring now to FIG. 2, a simplified messaging and processing flowdiagram of the system 100 for providing enhanced credit processing andmessaging is depicted. At block 202, the POS computing system 112 of themerchant 110 receives payment vehicle data corresponding to a paymentvehicle 104 tendered by the consumer 102 for a credit or paymenttransaction. The credit transaction can be associated with the purchaseof goods or services (e.g., a purchase event) from the merchant 110.

At decision block 204, the POS computing system 112 determines whetherthe credit transaction is an alternate routing candidate. For example,the POS computing system 112 determines whether messaging and processingfor the credit transaction should occur over the PIN debit network 150or if messaging and processing should occur over the card network(s)160. In the illustrative embodiment, the PIN debit network 150 isconfigured to communicate additional types of data that cannot becommunicated via the card network(s) 160 due to strict financialtransaction messaging specifications and protocols. If, in decisionblock 204, the POS computing system 112 determines that the credittransaction is an alternate routing candidate, processing advances todecision block 218. If, however, the POS computing system 112 insteaddetermines that the credit transaction is not an alternate routingcandidate, the POS computing system 112 transmits an authorizationrequest message for the credit transaction to the acquirer computingsystem 132 of the acquirer 130 for transmission to the issuer computingsystem 142 via the card network(s) 160. Processing then advances toblock 206.

In block 206, the acquirer computing system 132 receives theauthorization request message transmitted by the POS computing system112. Subsequently, in flow 208, the acquirer computing system 132transmits and/or forwards the received authorization request message tothe issuer computing system 142 via the card network(s) 160 according totraditional payment vehicle processing techniques and messaging. Inblock 210, upon receiving the authorization request message forwarded bythe acquirer computing system 132, the issuer computing system 142processes the received authorization request message. For example, theissuer computing system 142 can generate a corresponding authorizationresponse message based at least in part on, or otherwise as a functionof, the received authorization request message.

In flow 212, the issuer computing system 142 transmits the authorizationresponse message to the acquirer computing system 132 via the cardnetwork(s) 160. Subsequently, in block 214, the acquirer computingsystem 132 receives the authorization response message transmitted bythe issuer computing system 142. Upon receiving the authorizationresponse message, the acquirer computing system 132 transmits and/orforwards the authorization response message to the POS computing system112. In block 216, the POS computing system 112 finalizes the credittransaction corresponding to the purchase event based on the receivedauthorization response message.

In decision block 218, in response to determining that the credittransaction is an alternate routing candidate, the POS computing system112 determines whether enhanced and/or additional messaging is requiredfor the credit transaction. That is, the POS computing system 112 candetermine whether data and/or messaging in addition to the authorizationrequest message should be transmitted to the issuer computing system142. If, in decision block 218, the POS computing system 112 determinesthat enhanced and/or additional messaging is not required for the credittransaction, processing advances to flow 220 in which the POS computingsystem 112 transmits only the authorization request message directly tothe issuer computing system 142 via the PIN debit network 150. If,however, the POS computing system 112 determines instead that enhancedand/or additional messaging is required for the credit transaction,processing advances to flow 222 in which the POS computing system 112transmits the authorization request message and any additional messagingdirectly to the issuer computing system 142 via the PIN debit network150. In either case, processing advances to decision block 224.

In decision block 224, the issuer computing system 142 determineswhether a response from the consumer 102 is required to complete thecredit transaction or for any other purpose. For example, in someembodiments, the issuer computing system 142 can determine that aresponse from the consumer 102 can be required to accept an offerassociated with the credit transaction and/or a credit account of theconsumer 102. If, in decision block 224, the issuer computing system 142determines that a response from the consumer 102 is not required,processing advances to block 226.

In block 226, the issuer computing system 142 processes theauthorization request message. To do so, in some embodiments, the issuercomputing system 142 generates an authorization response message basedat least in part on, or otherwise as a function of, the authorizationrequest message received directly from the POS computing system 112.Subsequently, in flow 228, the issuer computing system 142 transmits theauthorization response message directly to the POS computing system 112via the PIN debit network 150. Next, in block 230, the POS computingsystem 112 finalizes the credit transaction corresponding to thepurchase event based on the received authorization response message.

Returning to decision block 224, if the issuer computing system 142determines instead that a response from the consumer 102 is required,processing advances to flow 232 in which the issuer computing system 142transmits a response request message directly to the POS computingsystem 112 via the PIN debit network 150. Subsequently, in block 234,the POS computing system 112 receives response data from the consumer102. As discussed, the response request message can be configured toelicit response data from the consumer 102.

After receiving the response data from the consumer 102, the POScomputing system 112, in flow 236, transmits the response data directlyto the issuer computing system 142 via the PIN debit network 150. Inblock 238, upon receipt of the response data from the POS computingsystem 112, the issuer computing system 142 processes the receivedresponse data. The process advances to block 226 in which the issuercomputing system 142 processes the authorization request message basedon the authorization request message initially received directly fromthe POS computing system 112 and the processed response data. To do so,in some embodiments, the issuer computing system 142 generates acorresponding authorization response message that can be transmitted tothe POS computing system 112 via the PIN debit network 150 as discussedabove.

Referring now to FIG. 3, a method 300 that may be executed by the POScomputing system 112 of the merchant 110 for leveraging the PIN debitnetwork 150 to provide enhanced credit processing and messaging beginswith block 302. In block 302, the POS computing system 112 receivespayment vehicle data corresponding to a payment vehicle 104 tendered bythe consumer 102 for a credit transaction or payment transaction. Thecredit transaction can be associated with the purchase of goods orservices (e.g., a purchase event). In some embodiments, the paymentvehicle data can include a bank identification number (BIN) or otherbank identifier associated with the payment vehicle 104 tendered in thecredit transaction, an account identifier associated with the paymentvehicle 104 tendered in the credit transaction, or any other type ofdata that communicates account information and/or informationcorresponding to the consumer 102.

In decision block 304, the POS computing system 112 determines whetherthe credit transaction is an alternate routing candidate. That is, thePOS computing system 112 determines whether the credit transaction is tobe routed to the issuer financial institution 140 via the cardnetwork(s) 160 using traditional credit processing techniques or whetherthe credit transaction, or a portion thereof, is to be routed to theissuer financial institution 140 via the PIN debit network 150. Asdiscussed, the PIN debit network 150 can be configured to communicateadditional types of data that cannot be communicated via the cardnetwork(s) 160 due to strict financial transaction messagingspecifications and protocols. In some embodiments, the POS computingsystem 112 determines whether the credit transaction is an alternaterouting candidate based on the BIN and/or account identifier associatedwith the payment vehicle 104 tendered for the credit transaction.Additionally or alternatively, the POS computing system 112 candetermine whether the credit transaction is an alternate routingcandidate based at least in part on, or otherwise as a function of,transaction interchange fees. For example, the POS computing system 112can determine that the credit transaction is an alternate routingcandidate based on determining that if routed via the PIN debit network150, lower transaction interchange fees would be levied on the credittransaction. In another example, the POS computing system 112 candetermine that the credit transaction is an alternate routing candidatebased on determining that two-way communications are required betweenthe issuer financial institution 140 and the consumer 102 to completethe credit or payment transaction. It should be appreciated that anyother transaction parameters or characteristics can be utilized by thePOS computing system 112 to determine whether the credit transaction isan alternate routing candidate. If, in decision block 304, the POScomputing system 112 determines that the credit transaction is analternate routing candidate, the method 300 advances to decision block310. If, however, the POS computing system 112 instead determines thatthe credit transaction is not an alternate routing candidate, the method300 advances to block 306.

In block 306, in response to determining that the credit transaction isnot an alternate routing candidate, the POS computing system 112transmits an authorization request message for the credit transaction tothe acquirer computing system 132 of the acquirer 130. It should beappreciated that the authorization request message can be transmittedand/or forwarded by the acquirer computing system 132 to the issuercomputing system 142 via the card network(s) 160 according totraditional payment vehicle processing techniques. Additionally, inblock 306, the POS computing system 112 receives an authorizationresponse message from the acquirer computing system 132. It should beappreciated that, in some embodiments, the authorization responsemessage can first be received by the acquirer computing system 132 fromthe issuer computing system 142 via the card network(s) 160 according totraditional payment vehicle processing techniques. In such embodiments,the acquirer computing system 132 can transmit and/or forward theauthorization response message to the POS computing system 112.

In block 308, the POS computing system 112 can finalize the credittransaction corresponding to the purchase event based on the receivedauthorization response message. For example, the POS computing system112 can generate a receipt for the credit transaction and/or thepurchase event based at least in part on, or otherwise as a function of,the received authorization response message. In other examples, the POScomputing system 112 can facilitate the settlement of funds associatedwith the credit transaction based on the received authorization responsemessage. It should be appreciated that the POS computing system 112 canperform any other transaction finalization processing based on thereceived authorization response message.

In decision block 310, in response to determining that the credittransaction is an alternate routing candidate, the POS computing system112 determines whether enhanced and/or additional messaging is requiredfor the credit transaction. That is, the POS computing system 112 candetermine whether data and/or messaging in addition to the authorizationrequest message should be transmitted to the issuer computing system 142via the PIN debit network 150. For example, in some embodiments, the POScomputing system 112 can determine whether application data for a newcredit account requested by the consumer 102 should be transmitted tothe issuer computing system 142 via the PIN debit network 150. Inanother example, the POS computing system 112 can determine whethercredit line increase request data should be transmitted to the issuercomputing system 142 via the PIN debit network 150. It should beappreciated that the POS computing system 112 can determine whether anyother type of data or information should be transmitted to the issuercomputing system 142 via the PIN debit network 150. If, in decisionblock 310, the POS computing system 112 determines that enhanced and/oradditional messaging is not required for the credit transaction, themethod 300 advances to block 312 in which the POS computing system 112transmits only the authorization request message directly to the issuercomputing system 142 via the PIN debit network 150. The method 300 thenadvances to decision block 316. If, however, the POS computing system112 determines instead that enhanced and/or additional messaging isrequired for the credit transaction, the method 300 advances to block314 in which the POS computing system 112 transmits the authorizationrequest message and any additional messaging or data directly to theissuer computing system 142 via the PIN debit network 150.

In decision block 316, the POS computing system 112 determines whether aresponse request message is received from the issuer computing system142. The response request message can include a request for responsedata from the consumer 102 and can be received via the PIN debit network150. As discussed below, the POS computing system 112 can elicit aresponse from the consumer 102 based on the response request message.For example, in some embodiments, the response request message caninclude a financing offer from the issuer financial institution 140 (ora third party promotion entity) for the credit transaction. Thefinancing offer (including the offered terms) can be presented to theconsumer 102 via the POS computing system 112 and a response can beelicited. In other examples, the response request message can include anoffer for a new credit account or an offer to increase the credit limitof an existing credit account. Of course, the response request messagecan include any other type of data or offer for eliciting a responsefrom the consumer 102. It should be appreciated that such types ofbi-directional communications are not possible over the card network(s)160 due to the strict financial transaction messaging specifications andprotocols employed. If, in decision block 316, the POS computing system112 determines that a response request message is not received from theissuer computing system 142 via the PIN debit network 150, the method300 advances to decision block 318. If, however, the POS computingsystem 112 determines instead that a response request message isreceived from the issuer computing system 142 via the PIN debit network150, the method 300 advances to block 322.

In decision block 318, in response to determining that a responserequest message is not received from the issuer computing system 142 viathe PIN debit network 150, the POS computing system 112 determineswhether an authorization response message is received directly from theissuer computing system 142 via the PIN debit network 150. Theauthorization response message can be based on the authorization requestmessage initially transmitted from the POS computing system 112 in block312 or block 314. If, in decision block 318, the POS computing system112 determines that an authorization response message is not receivedfrom the issuer computing system 142, the method 300 loops back todecision block 316 and the POS computing system 112 determines whether aresponse request message is received from the issuer computing system142 via the PIN debit network 150. If, however, in decision block 318,the POS computing system 112 determines instead that an authorizationresponse message is received from the issuer computing system 142 viathe PIN debit network 150, the method 300 advances to block 320 in whichthe POS computing system 112 finalizes the credit transactioncorresponding to the purchase event based on the received authorizationresponse message.

In block 322, in response to determining that a response request messageis received from the issuer computing system 142 via the PIN debitnetwork 150 in decision block 316, the POS computing system 112 receivesresponse data from the consumer 102. As discussed above, the POScomputing system 112 can elicit response data from the consumer 102based at least in part on, or otherwise a function of, the responserequest message received from the issuer computing system 142 via thePIN debit network 150. For example, in embodiments in which the responserequest message received from the issuer computing system 142 includes afinancing offer for the credit transaction, the POS computing system 112can elicit an acceptance and any related information from the consumer102 for the financing offer. It should be appreciated that the POScomputing system 112 can elicit and receive any other type of responsedata from the consumer 102 as a function of the response request messagereceived from the issuer computing system 142.

In block 324, the POS computing system 112 can transmit the responsedata received from the consumer 102 to the issuer computing system 142via the PIN debit network 150. Subsequently, in block 326, the POScomputing system 112 can receive an authorization response messagedirectly from the issuer computing system 142 via the PIN debit network150. The authorization response message can be based on theauthorization request message initially transmitted by the POS computingsystem 112 in block 312 or block 314 and the response data transmittedby the POS computing system 112 in block 324. In block 328, afterreceiving the authorization response message from the issuer computingsystem 142, the POS computing system 112 finalizes the credittransaction corresponding to the purchase event based on the receivedauthorization response message.

Referring now to FIG. 4, a method 400 that may be executed by the issuercomputing system 142 of the issuer financial institution 140 forleveraging the PIN debit network 150 to provide enhanced creditprocessing and messaging begins with decision block 402. In decisionblock 402, the issuer computing system 142 determines whether anauthorization request message is received from the POS computing system112 (or an intermediary device such as the acquirer computing system132). The authorization request message corresponds to a credittransaction or payment transaction for a purchase event. If, in decisionblock 402, the issuer computing system 142 determines that anauthorization request message is received from the POS computing system112, the method 400 advances to decision block 404. If, however, theissuer computing system 142 determines instead that an authorizationrequest message is not received from the POS computing system 112, themethod 400 loops back to decision block 402 and the issuer computingsystem 142 continues monitoring for receipt of an authorization requestmessage from the POS computing system 112 (or an intermediary device).

In decision block 404, the issuer computing system 142 determineswhether the authorization request message was received from the POScomputing system 112 via the card network(s) 160 or via the PIN debitnetwork 150. As discussed, in some embodiments, the authorizationrequest message can be received via the POS computing system 112 via thecard network(s) 160 using traditional credit processing techniques. Insuch embodiments, the authorization request message can first bereceived by the acquirer computing system 132 (or another intermediarydevice) and then forwarded over the card network(s) 160 to the issuercomputing system 142 according to traditional credit processingmessaging and processing. In other embodiments, the authorizationrequest message can be received directly from the POS computing system112 via the PIN debit network 150. If, in decision block 404, the issuercomputing system 142 determines that the authorization request messageis received from the POS computing system via the card network(s) 160(and any intermediary computing systems), the method 400 advances toblock 406. If, however, the issuer computing system 142 determinesinstead that the authorization request message is received directly fromthe POS computing system 112 via the PIN debit network 150, the method400 advances to decision block 410.

In block 406, in response to determining that the authorization requestmessage is received via the card network(s) 160, the issuer computingsystem 142 processes the authorization request message according totraditional credit processing techniques. For example, the issuercomputing system 142 can generate an authorization response messagebased at least in part on, or otherwise as a function of, the receivedauthorization request message. Subsequently, in block 408, the issuercomputing system 142 transmits the authorization response message to thePOS computing system 112 via the card network(s) 160 (and anyintermediary computing devices) according to traditional creditprocessing techniques and messaging protocols.

In decision block 410, in response to determining that the authorizationrequest message is received via the PIN debit network 150, the issuercomputing system 142 determines whether a consumer response is required.In some embodiments, the consumer response can be required to completethe credit transaction. In other embodiments, the consumer response canbe an offer for additional services, an offer for a new credit account,a request for acceptance of new and/or modified account terms andconditions, an offer to increase a credit limit, a balance transferoffer, a request for acknowledgement of applicable interest rates orfees, a discount offer, or any other type of offer and/or communicationrequiring a response from the consumer 102. If, in decision block 410,the issuer computing system 142 determines that a response from theconsumer 102 is required, the method 400 advances to block 416. If,however, the issuer computing system 142 determines instead that aresponse from the consumer 102 is not required, the method 400 advancesto block 412.

In block 412, in response to determining that a response from theconsumer 102 is not required, the issuer computing system 142 processesthe authorization request message. To do so, in some embodiments, theissuer computing system 142 generates an authorization response messagebased at least in part on, or otherwise as a function of, theauthorization request message received in block 402. Subsequently, inblock 414, the issuer computing system 142 transmits the authorizationresponse message to the POS computing system 112 via the PIN debitnetwork 150.

In block 416, in response to determining that a response from theconsumer 102 is required, the issuer computing system 142 transmits aresponse request message to the POS computing system 112 via the PINdebit network 150. The response request message can include a requestfor response data from the consumer 102. As discussed, in someembodiments, the response request message can include an interactiveoffer to be presented to the consumer 102 via the POS computing system112. It should be appreciated that such types of bi-directionalcommunications and requests are not possible over the card network(s)160 due to the strict financial transaction messaging specifications andprotocols employed.

In block 418, the issuer computing system 142 receives response datafrom the POS computing system 112 via the PIN debit network 150. Thereceived response data can be based on the response request messagetransmitted to the POS computing system 112 in block 416. Subsequently,in block 420, the issuer computing system 142 processes the receivedresponse data. For example, in some embodiments, the issuer computingsystem 142 can determine whether the consumer 102 accepted a financingoffer for the credit transaction, accepted an offer for increasing theconsumer's 102 credit limit, accepted or requested a balance transfer,and/or accepted or requested any other type of offer or service.

In block 422, the issuer computing system 142 processes theauthorization request message based on the authorization request messageinitially received from the POS computing system 112 in block 402 andthe response data received from the POS computing system 112 in block418 and processed by the issuer computing system 142 in block 420. To doso, in some embodiments, the issuer computing system 142 generates acorresponding authorization response message. Subsequently, in block424, the issuer computing system 142 transmits the authorizationresponse message to the POS computing system 112 via the PIN debitnetwork 150 for finalization of the credit/payment transaction.

Referring now to FIG. 5, an alternative simplified messaging andprocessing flow diagram of the system 100 for providing enhanced creditprocessing and messaging is depicted. At block 502, the POS computingsystem 112 of the merchant 110 receives payment vehicle datacorresponding to a payment vehicle 104 tendered by the consumer 102 fora credit or payment transaction. The credit transaction can beassociated with the purchase of goods or services (e.g., a purchaseevent) from the merchant 110.

At decision block 504, the POS computing system 112 determines whetherthe credit transaction is an alternate routing candidate. For example,the POS computing system 112 determines whether all or a portion ofmessaging and processing for the credit transaction should occur overthe PIN debit network 150 or if all or a portion of messaging andprocessing should occur over the card network(s) 160. In embodimentssuch as the one illustratively shown in FIG. 5, the PIN debit network150 can be configured to communicate additional types of data thatcannot be communicated via the card network(s) 160 due to strictfinancial transaction messaging specifications and protocols. In suchembodiments, the POS computing system 112 can determine whether thecredit transaction is an alternate routing candidate based on whetherspecial or enhanced data is to be communicated between the POS computingsystem 112 and the issuer computing system 142 as part of the credittransaction. Such special or enhanced data can include data orinformation in addition to conventional credit processing data ormessages (e.g., authorization request messages, authorization responsemessages, etc.). For example, the special or enhanced data can beembodied as a loyalty account identifier associated with the consumer102, SKU data corresponding to purchased products or services,promotional offer data, financing offer data, payment card applicationdata, credit line increase data, and/or any other type of data thatcannot be communicated over traditional payment card networks 160 due tostrict financial transaction messaging specifications (e.g., ISO 8583,etc.) and/or protocol requirements employed. If, in decision block 504,the POS computing system 112 determines that the credit transaction isnot an alternate routing candidate, the POS computing system 112transmits an authorization request message for the credit transaction tothe acquirer computing system 132 of the acquirer 130 for transmissionto the issuer computing system 142 via the card network(s) 160.Processing then advances to block 506.

In block 506, the acquirer computing system 132 receives theauthorization request message transmitted by the POS computing system112. Subsequently, in flow 508, the acquirer computing system 132transmits and/or forwards the received authorization request message tothe issuer computing system 142 via the card network(s) 160 according totraditional payment vehicle processing techniques and messaging. Inblock 510, upon receiving the authorization request message forwarded bythe acquirer computing system 132, the issuer computing system 142processes the received authorization request message. For example, theissuer computing system 142 can generate a corresponding authorizationresponse message based at least in part on, or otherwise as a functionof, the received authorization request message.

In flow 512, the issuer computing system 142 transmits the authorizationresponse message to the acquirer computing system 132 via the cardnetwork(s) 160. Subsequently, in block 514, the acquirer computingsystem 132 receives the authorization response message transmitted bythe issuer computing system 142. Upon receiving the authorizationresponse message, the acquirer computing system 132 transmits and/orforwards the authorization response message to the POS computing system112. In block 516, the POS computing system 112 finalizes the credittransaction corresponding to the purchase event based on the receivedauthorization response message.

Referring back to decision block 504, if the POS computing system 112determines instead that the credit transaction is an alternate routingcandidate, processing advances to block 518. In block 518, the POScomputing system 112 splits the credit transaction into two or moremessages. For example, in the illustrative embodiment, the POS computingsystem 112 splits the credit transaction into an authorization requestmessage and an enhanced data message. The authorization request messagecan be formatted according to conventional financial transactionmessaging specifications (e.g., ISO 8583, etc.) and/or protocols fortransmission via the card network(s) 160. The enhanced data message caninclude one or more additional types of credit transaction data (e.g.,special or enhanced data message) that cannot be communicated via thecard network(s) 160, as discussed above.

Additionally, in block 518, after splitting the credit transaction, thePOS computing system 112 transmits the authorization request message forthe credit transaction to the acquirer computing system 132 of theacquirer 130 for transmission to the issuer computing system 142 via thecard network(s) 160. Processing then advances to block 520 in which theacquirer computing system 132 receives the authorization request messagetransmitted by the POS computing system 112. Subsequently, in flow 522,the acquirer computing system 132 transmits and/or forwards the receivedauthorization request message to the issuer computing system 142 via thecard network(s) 160 according to traditional payment vehicle processingtechniques and messaging. In some embodiments, in block 524, uponreceiving the authorization request message forwarded by the acquirercomputing system 132, the issuer computing system 142 queues thereceived authorization request message for subsequent processing.

Contemporaneously with, or at substantially the same time as, theauthorization request message for the credit transaction is transmittedto acquirer computing system 132, the POS computing system 112, in flow526, transmits the enhanced data message to the issuer computing system142 via the PIN debit network 150. It should be appreciated thatalthough the authorization request message and the enhanced data messageare transmitted in parallel in the illustrative embodiment, theauthorization request message and the enhanced data message can betransmitted at different times, in other embodiments. For example, insome embodiments, the POS computing system 112 can transmit theauthorization request message to the issuer computing system 142 via theacquirer computing system 132 and card network(s) 160 prior totransmitting the enhanced data message to the issuer computing system142 via the PIN debit network 150. In such embodiments and as discussedabove, the issuer computing system 142 can be configured to queue thereceived authorization request message until the enhanced data messageis received (block 524).

In block 528, the issuer computing system 142 matches the authorizationrequest message received via the card network(s) 160 to the enhanceddata message received via the PIN debit network 150. To do so, in someembodiments, the enhanced data message can include an identifier thatmatches a unique identifier of the authorization request message. Forexample, the enhanced data message can include an identifier thatmatches a unique transaction identifier included in the authorizationrequest message. It should be appreciated, however, that the enhanceddata message and the authorization request message can include any othertype of data or keys capable of being matched by the issuer computingsystem 142.

Subsequently, in decision block 530, the issuer computing system 142determines whether a response from the consumer 102 is required tocomplete the credit transaction or for any other purpose. For example,in some embodiments, the issuer computing system 142 can determine thata response to an offer provided to the consumer 102 is required. If, indecision block 530, the issuer computing system 142 determines that aresponse from the consumer 102 is not required, processing advances toblock 540.

In block 540, the issuer computing system 142 processes theauthorization request message based at least in part on, or otherwise asa function of, the enhanced data message matched thereto. To do so, insome embodiments, the issuer computing system 142 generates anauthorization response message based at least in part on theauthorization request message received from the POS computing system 112via the card network(s) 160 and the matching enhanced data messagereceived from the POS computing system 112 via the PIN debit network150. Subsequently, in flow 542, the issuer computing system 142transmits the generated authorization response message to the acquirercomputing system 132 via the card network(s) 160. In block 544, theacquirer computing system 132 receives the authorization responsemessage transmitted by the issuer computing system 142. Upon receivingthe authorization response message, the acquirer computing system 132transmits and/or forwards the authorization response message to the POScomputing system 112. Processing then advances to block 516 in which thePOS computing system 112 finalizes the credit transaction correspondingto the purchase event based on the received authorization responsemessage.

Returning to decision block 530, if the issuer computing system 142determines instead that a response from the consumer 102 is required,processing advances to flow 532 in which the issuer computing system 142transmits a response request message directly to the POS computingsystem 112 via the PIN debit network 150. Subsequently, in block 534,the POS computing system 112 receives response data from the consumer102. As discussed, the response request message can be configured toelicit response data from the consumer 102.

After receiving the response data from the consumer 102, the POScomputing system 112, in flow 536, transmits the response data directlyto the issuer computing system 142 via the PIN debit network 150. Inblock 538, upon receipt of the response data from the POS computingsystem 112, the issuer computing system 142 processes the receivedresponse data. The process advances to block 540 in which the issuercomputing system 142 processes the authorization request message basedat least in part on, or otherwise as a function of, the matchingenhanced data message and the processed response data. To do so, in someembodiments, the issuer computing system 142 generates a correspondingauthorization response message. Processing advances to flow 542, block544, and block 516 in which the issuer computing system 142 transmitsthe generated authorization response message to the acquirer computingsystem 132 via the card network(s) 160, the acquirer computing system132 transmits and/or forwards the authorization response message to thePOS computing system 112, and the POS computing system 112 finalizes thecredit transaction corresponding to the purchase event based on thereceived authorization response message.

Referring now to FIG. 6, a method 600 that may be executed by the POScomputing system 112 of the merchant 110 for leveraging the PIN debitnetwork 150 and the card network(s) 160 to provide enhanced creditprocessing and messaging begins with block 602. In block 602, the POScomputing system 112 receives payment vehicle data corresponding to apayment vehicle 104 tendered by the consumer 102 for a credittransaction or payment transaction. The credit transaction can beassociated with the purchase of goods or services (e.g., a purchaseevent). In some embodiments, the payment vehicle data can include a bankidentification number (BIN) or other bank identifier associated with thepayment vehicle 104 tendered in the credit transaction, an accountidentifier associated with the payment vehicle 104 tendered in thecredit transaction, or any other type of data that communicates accountinformation and/or information corresponding to the consumer 102.

In decision block 604, the POS computing system 112 determines whetherthe credit transaction is an alternate routing candidate. That is, thePOS computing system 112 determines whether the credit transaction, or aportion thereof, is to be routed to the issuer financial institution 140via the card network(s) 160 using traditional credit processingtechniques or whether the credit transaction, or a portion thereof, isto be routed to the issuer financial institution 140 via the PIN debitnetwork 150. As discussed, the PIN debit network 150 can be configuredto communicate additional types of data that cannot be communicated viathe card network(s) 160 due to the strict financial transactionmessaging specifications and protocols employed. In some embodiments,the POS computing system 112 determines whether the credit transactionis an alternate routing candidate based on the BIN and/or accountidentifier associated with the payment vehicle 104 tendered for thecredit transaction. Additionally or alternatively, the POS computingsystem 112 can determine that the credit transaction is an alternaterouting candidate based on determining that two-way communications arerequired between the issuer financial institution 140 and the consumer102 to complete the credit or payment transaction.

In some embodiments, the POS computing system 112 can also determinewhether the credit transaction is an alternate routing candidate basedon whether a special or enhanced data message is to be communicatedbetween the POS computing system 112 and the issuer computing system 142as part of the credit transaction. Such special or enhanced data messagecan include data or information in addition to conventional creditprocessing data or messages (e.g., authorization request messages,authorization response messages, etc.). For example, the special orenhanced data message can be embodied as or include a loyalty accountidentifier associated with the consumer 102, SKU data corresponding topurchased products or services, promotional offer data, financing offerdata, payment card application data, credit line increase data, and/orany other type of data that cannot be communicated over traditionalpayment card networks 160 due to the strict financial transactionmessaging specifications (e.g., ISO 8583, etc.) and/or protocolrequirements employed. It should be appreciated that any othertransaction parameters or characteristics can be utilized by the POScomputing system 112 to determine whether the credit transaction is analternate routing candidate. If, in decision block 604, the POScomputing system 112 determines that the credit transaction is not analternate routing candidate, the method 600 advances to block 606.

In block 606, in response to determining that the credit transaction isnot an alternate routing candidate, the POS computing system 112transmits an authorization request message for the credit transaction tothe acquirer computing system 132 of the acquirer 130. It should beappreciated that the authorization request message can be transmittedand/or forwarded by the acquirer computing system 132 to the issuercomputing system 142 via the card network(s) 160 according totraditional payment vehicle processing techniques. Additionally, inblock 606, the POS computing system 112 receives an authorizationresponse message from the acquirer computing system 132. It should beappreciated that, in some embodiments, the authorization responsemessage can first be received by the acquirer computing system 132 fromthe issuer computing system 142 via the card network(s) 160 according totraditional payment vehicle processing techniques. In such embodiments,the acquirer computing system 132 can transmit and/or forward theauthorization response message to the POS computing system 112.

In block 608, the POS computing system 112 finalizes the credittransaction corresponding to the purchase event based on the receivedauthorization response message. For example, the POS computing system112 can generate a receipt for the credit transaction and/or thepurchase event based at least in part on, or otherwise as a function of,the received authorization response message. In other examples, the POScomputing system 112 can facilitate the settlement of funds associatedwith the credit transaction based on the received authorization responsemessage. It should be appreciated that the POS computing system 112 canperform any other transaction finalization processing based on thereceived authorization response message.

Referring back to decision block 604, if the POS computing system 112determines instead that the credit transaction is an alternate routingcandidate, processing advances to block 610. In block 610, the POScomputing system 112 splits the credit transaction into two or moremessages. For example, in the illustrative embodiment, the POS computingsystem 112 splits the credit transaction into an authorization requestmessage and an enhanced data message. The authorization request messagecan be formatted according to conventional financial transactionmessaging specifications (e.g., ISO 8583, etc.) and/or protocols fortransmission via the card network(s) 160. The enhanced data message caninclude one or more additional types of credit transaction data thatcannot be communicated via the card network(s) 160, as discussed above.The method 600 then advances in parallel to blocks 612 and 614. Itshould be appreciated that in some embodiments, the method 600 advancesfirst to block 612, advances first to block 614, or advances to block612 contemporaneously with, or at substantially the same time as,advancing to block 614.

In block 612, the POS computing system 112 transmits the authorizationrequest message for the credit transaction to the issuer computingsystem 142 via the acquirer computing system 132 and the card network(s)160 according to traditional payment vehicle processing techniques. Inblock 614, the POS computing system 112 transmits the enhanced datamessage to the issuer computing system 142 via the PIN debit network150. In embodiments in which the POS computing system 112 transmits theauthorization request message to the issuer computing system 142 priorto transmitting the enhanced data message, the issuer computing system142 can be configured to queue the authorization request message untilthe enhanced data message is received from the POS computing system 112.After transmitting the authorization request message and the enhanceddata message, the method 600 advances to decision block 616.

In decision block 616, the POS computing system 112 determines whether aresponse request message is received from the issuer computing system142. The response request message can include a request for responsedata from the consumer 102 and can be received via the PIN debit network150. As discussed below, the POS computing system 112 can elicit aresponse from the consumer 102 based on the response request message.For example, in some embodiments, the response request message caninclude a financing offer from the issuer financial institution 140 (ora third party promotion entity) for the credit transaction. Thefinancing offer (including the offered terms) can be presented to theconsumer 102 via the POS computing system 112 and a response can beelicited. In other examples, the response request message can include anoffer for a new credit account or an offer to increase the credit limitof an existing credit account. Of course, the response request messagecan include any other type of data or offer for eliciting response(s)from the consumer 102. It should be appreciated that such types ofbi-directional communications are not possible over the card network(s)160 due to the strict financial transaction messaging specifications andprotocols employed. If, in decision block 616, the POS computing system112 determines that a response request message is not received from theissuer computing system 142 via the PIN debit network 150, the method600 advances to decision block 618.

In decision block 618, in response to determining that a responserequest message is not received from the issuer computing system 142 viathe PIN debit network 150, the POS computing system 112 determineswhether an authorization response message is received from the issuercomputing system 142 via the card network(s) 160. The authorizationresponse message can be based on the authorization request message andthe enhanced data message initially transmitted by the POS computingsystem 112 in block 612 and block 614. If, in decision block 618, thePOS computing system 112 determines that an authorization responsemessage is not received from the issuer computing system 142, the method600 loops back to decision block 616 and the POS computing system 112determines whether a response request message is received from theissuer computing system 142 via the PIN debit network 150. If, however,in decision block 618, the POS computing system 112 determines insteadthat an authorization response message is received from the issuercomputing system 142 via the card network(s) 160, the method 600advances to block 620 in which the POS computing system 112 finalizesthe credit transaction corresponding to the purchase event based on thereceived authorization response message.

Referring back to decision block 616, if the POS computing system 112determines instead that a response request message is received from theissuer computing system 142 via the PIN debit network 150, the method600 advances to block 622. In block 622, the POS computing system 112receives response data from the consumer 102. As discussed above, thePOS computing system 112 can elicit response data from the consumer 102based at least in part on, or otherwise a function of, the responserequest message received from the issuer computing system 142 via thePIN debit network 150. For example, in embodiments in which the responserequest message received from the issuer computing system 142 includes afinancing offer for the credit transaction, the POS computing system 112can elicit an acceptance and any related information from the consumer102 for the financing offer. It should be appreciated that the POScomputing system 112 can elicit and receive any other type of responsedata from the consumer 102 as a function of the response request messagereceived from the issuer computing system 142.

In block 624, the POS computing system 112 transmits the response datareceived from the consumer 102 to the issuer computing system 142 viathe PIN debit network 150. Subsequently, in block 626, the POS computingsystem 112 receives an authorization response message from the issuercomputing system 142 via card network(s) 160. The authorization responsemessage can be based on the authorization request message initiallytransmitted by the POS computing system 112 in block 612, the enhanceddata message transmitted by the POS computing system 112 in block 614,and the response data transmitted by the POS computing system 112 inblock 624. In block 628, after receiving the authorization responsemessage from the issuer computing system 142, the POS computing system112 finalizes the credit transaction corresponding to the purchase eventbased on the received authorization response message.

Referring now to FIG. 7, a method 700 that may be executed by the issuercomputing system 142 of the issuer financial institution 140 forleveraging the PIN debit network 150 and the card network(s) 160 toprovide enhanced credit processing and messaging begins with block 702.In block 702, the issuer computing system 142 receives an authorizationrequest message from the POS computing system 112 via the cardnetwork(s) 160 and any intermediary devices such, for example, theacquirer computing system 132. The authorization request messagecorresponds to a credit transaction or payment transaction for apurchase event.

Contemporaneously with, or at substantially the same time as, theauthorization request message for the credit transaction is receivedfrom the POS computing system 112, the issuer computing system 142receives, in block 706, an enhanced data message from the POS computingsystem 112 via the PIN debit network 150. It should be appreciated thatalthough the authorization request message and the enhanced data messageare received in parallel in the illustrative embodiment, theauthorization request message and the enhanced data message can bereceived at different times, in other embodiments. For example, in someembodiments, the issuer computing system 142 can receive theauthorization request message from the POS computing system 112 via thecard network(s) 160 prior to receiving the enhanced data message fromthe POS computing system 112 via the PIN debit network 150. In suchembodiments, in block 704, the issuer computing system 142 can beconfigured to queue the received authorization request message until theenhanced data message is received (block 706).

Subsequently, in block 708, the issuer computing system 142 matches theauthorization request message received via the card network(s) 160 tothe enhanced data message received via the PIN debit network 150. To doso, in some embodiments, the enhanced data message can include anidentifier that matches a unique identifier of the authorization requestmessage. For example, the enhanced data message can include anidentifier that matches a unique transaction identifier included in theauthorization request message. It should be appreciated, however, thatthe enhanced data message and the authorization request message caninclude any other type of data or keys capable of being matched by theissuer computing system 142.

In decision block 710, the issuer computing system 142 determineswhether a response from the consumer 102 is required to complete thecredit transaction or for any other purpose. For example, in someembodiments, the issuer computing system 142 can determine that aresponse to an offer provided to the consumer 102 is required. If, indecision block 710, the issuer computing system 142 determines that aresponse from the consumer 102 is not required, the method 700 advancesto block 712.

In block 712, the issuer computing system 142 processes theauthorization request message based at least in part on, or otherwise asa function of, the enhanced data message matched thereto. To do so, insome embodiments, the issuer computing system 142 generates anauthorization response message based at least in part on theauthorization request message received from the POS computing system 112via the card network(s) 160 and the matching enhanced data messagereceived from the POS computing system 112 via the PIN debit network150. The method 700 advances to block 724 in which the issuer computingsystem 142 transmits the generated authorization response message to thePOS computing system 112 via the card network(s) 160 and anyintermediary devices (e.g., the acquirer computing system 132, etc.).The POS computing system 112 can then process and finalize the credittransaction based on the received authorization response message, asdiscussed above.

Referring back to decision block 710, if the issuer computing system 142determines instead that a response from the consumer 102 is required,the method 700 advances to block 714 in which the issuer computingsystem 142 transmits a response request message directly to the POScomputing system 112 via the PIN debit network 150. As discussed, theresponse request message can be configured to elicit response data fromthe consumer 102 via the POS computing system 112 (or a computing orinput device associated therewith). Subsequently, in block 716, theissuer computing system 142 receives response data from the POScomputing system 112 via the PIN debit network 150. In block 720, uponreceipt of the response data from the POS computing system 112, theissuer computing system 142 processes the received response data. Themethod 700 then advances to block 722 in which the issuer computingsystem 142 processes the authorization request message based at least inpart on, or otherwise as a function of, the matching enhanced datamessage and the processed response data. To do so, in some embodiments,the issuer computing system 142 generates a corresponding authorizationresponse message. The method 700 advances to block 724 in which theissuer computing system 142 transmits the generated authorizationresponse message to the POS computing system 112 via the card network(s)160 and any intermediary devices (e.g., the acquirer computing system132, etc.). The POS computing system 112 can then process and finalizethe credit transaction based on the received authorization responsemessage, as discussed above.

Referring now to FIG. 8, in one embodiment, a system 800 for providingcredit processing and messaging includes a merchant 810, a merchantpoint of sale (POS) computing system 812, an acquirer 830, an acquirercomputing system 832, an issuer financial institution 840, an issuercomputing system 842, a PIN debit network 850, and one or more cardnetworks 860. The system 800 can be embodied as an alternativearrangement to the system 100 illustratively shown in FIG. 1. As such,the merchant 810, merchant POS computing system 812, acquirer 830,acquirer computing system 832, issuer financial institution 840, issuercomputing system 842, PIN debit network 850, and payment card network(s)840 of the system 800 of FIG. 8 can be functionally or architecturallysimilar to, or the same as, in many respects to the merchant 110,merchant POS computing system 112, acquirer 130, acquirer computingsystem 132, issuer financial institution 140, issuer computing system142, PIN debit network 150, and payment card network(s) 160 of thesystem 100 of FIG. 1. Additionally, the consumer 802 and payment vehicle804 illustratively shown in FIG. 8 can be substantially similar to, orthe same as, the consumer 102 and payment vehicle 104 illustrativelyshown in FIG. 1 and described above.

In some embodiments, the acquirer computing system 832 is configured toselectively transmit and/or route all or a portion of data and messagingassociated with a credit transaction to the issuer computing system 842via the card network(s) 860 and/or the PIN debit network 850. In suchembodiments, the POS computing system 812 receives payment vehicle dataassociated with a payment vehicle 804 tendered by a consumer 802 for acredit transaction. The credit transaction can correspond to thepurchase of goods or services (e.g., a purchase event) by the consumer802. Upon receiving the payment vehicle data, the POS computing system812 transmits transaction-specific data (e.g., a transaction amount, aBIN or other bank identifier associated with the payment vehicle 804tendered in the credit transaction, an account identifier associatedwith the payment vehicle 804 tendered in the credit transaction, amerchant identifier, etc.) to the acquirer computing system 832.Subsequently, the acquirer computing system 832 can determine whetherall or a portion of data or messaging associated with the credittransaction (e.g., authorization request messages, authorizationresponse messages, etc.) should be transmitted to the issuer computingsystem 842 via the card network(s) 860 or whether all or a portion ofthe data or messaging associated with the credit transaction should betransmitted to the issuer computing system 842 via the PIN debit network850. To do so, in some embodiments, the acquirer computing system 832can analyze the transaction-specific data received from the POScomputing system 812. For example, in some embodiments, the acquirercomputing system 832 can be configured to determine that data andmessaging (e.g., authorization request messages, authorization responsemessages, etc.) corresponding to the credit transaction should betransmitted to, or received from, the issuer computing system 842 viathe PIN debit network 850 based on the BIN and/or account identifierassociated with the payment vehicle 804 tendered in the credittransaction. In other examples, the acquirer computing system 832 can beconfigured to determine that the data and messaging corresponding to thecredit transaction should be transmitted to, or received from, theissuer computing system 842 via the PIN debit network 850 based ondetermining that lower transaction interchange fess would be levied onthe credit transaction if the data and messaging corresponding to thecredit transaction are transmitted or routed via the PIN debit network850 rather than the card network(s) 860. It should be appreciated thatany other transaction parameters or characteristics can be utilized bythe acquirer computing system 832 to determine whether the data andmessaging corresponding to the credit transaction should be transmittedto, or received from, the issuer computing system 842 via the PIN debitnetwork 850 or the card network(s) 860.

Additionally, in some embodiments, the PIN debit network 850 can beleveraged as an out-of-band communications network configured to supporttransmission of enhanced or enriched messages between the POS computingsystem 812 of the merchant 810 and the issuer computing system 842 ofthe issuer financial institution 840. To do so, in addition totransmitting the standard or conventional types of transaction-specificdata (e.g. a transaction amount, a BIN or other bank identifier, anaccount identifier, a merchant identifier, etc.) associated with thecredit transaction to the acquirer computing system 832, the POScomputing system 812 can also transmit additional or non-conventionaltypes of transaction-specific data (e.g., a loyalty account identifierassociated with the consumer 802, SKU data corresponding to purchasedproducts or services, promotional offer data, financing offer data,payment card application data, credit line increase data, etc.). Uponreceiving the additional transaction-specific data (e.g., special orenhanced transaction data), the acquirer computing system 832 can beconfigured to split the credit transaction into two or more messages.For example, in some embodiments, the acquirer computing system 832splits the credit transaction into an authorization request message andan enhanced data message. The authorization request message can beformatted according to conventional financial transaction messagingspecifications (e.g., ISO 8583, etc.) and/or protocols for transmissionvia the card network(s) 860. The enhanced data message can includespecial or enhanced transaction data that cannot be communicated via thecard network(s) 860 due to the strict financial transaction messagingspecifications (e.g., ISO 8583, etc.) and/or protocol requirementsemployed. Thereafter, the acquirer computing system 832 cantransmit/route the authorization request message to the issuer computingsystem 842 via the card network(s) 860. Contemporaneously with, or atsubstantially the same time as, the authorization request message forthe credit transaction is transmitted to issuer computing system 842 viathe card network(s) 860, the acquirer computing system 832 cantransmit/route the enhanced data message to issuer computing system 842via the PIN debit network 850. Subsequently, the issuer computing system842 matches the authorization request message received via the cardnetwork(s) 860 to the enhanced data message received via the PIN debitnetwork 850. In some embodiments, the issuer computing system canrequest and receive consumer response data from the POS computing system812 via the PIN debit network 850. In the illustrative embodiment, theauthorization request message is processed by the issuer computingsystem 842 based at least in part on, or otherwise as a function of, thereceived enhanced data message and, if any, the received consumerresponse data. Thereafter, the issuer computing system 842 generates andtransmits a corresponding authorization response message, which can beselectively transmitted to the acquirer computing system 832 via the PINdebit network 850 and/or the card network(s) 860. The acquirer computingsystem 832 can then forward the received authorization response messageto the POS computing system 812 via the PIN debit network 850 forfinalization of the credit transaction.

The systems, apparatuses, devices, and methods disclosed herein aredescribed in detail by way of examples and with reference to thefigures. The examples discussed herein are examples only and areprovided to assist in the explanation of the apparatuses, devices,systems and methods described herein. None of the features or componentsshown in the drawings or discussed herein should be taken as mandatoryfor any specific implementation of any of these the apparatuses,devices, systems or methods unless specifically designated as mandatory.In addition, elements illustrated in the figures are not necessarilydrawn to scale for simplicity and clarity of illustration. For ease ofreading and clarity, certain components, modules, or methods can bedescribed solely in connection with a specific figure. In thisdisclosure, any identification of specific techniques, arrangements,etc. are either related to a specific example presented or are merely ageneral description of such a technique, arrangement, etc.Identifications of specific details or examples are not intended to be,and should not be, construed as mandatory or limiting unlessspecifically designated as such. Any failure to specifically describe acombination or sub-combination of components should not be understood asan indication that any combination or sub-combination is not possible.It will be appreciated that modifications to disclosed and describedexamples, arrangements, configurations, components, elements,apparatuses, devices, systems, methods, etc. can be made and can bedesired for a specific application. Also, for any methods described,regardless of whether the method is described in conjunction with a flowdiagram, it should be understood that unless otherwise specified orrequired by context, any explicit or implicit ordering of stepsperformed in the execution of a method does not imply that those stepsmust be performed in the order presented but instead can be performed ina different order or in parallel.

Reference throughout the specification to “various embodiments,” “someembodiments,” “one embodiment,” “some example embodiments,” “one exampleembodiment,” or “an embodiment” means that a particular feature,structure, or characteristic described in connection with any embodimentis included in at least one embodiment. Thus, appearances of the phrases“in various embodiments,” “in some embodiments,” “in one embodiment,”“some example embodiments,” “one example embodiment,” or “in anembodiment” in places throughout the specification are not necessarilyall referring to the same embodiment. Furthermore, the particularfeatures, structures or characteristics can be combined in any suitablemanner in one or more embodiments.

Throughout this disclosure, references to components or modulesgenerally refer to items that logically can be grouped together toperform a function or group of related functions. Like referencenumerals are generally intended to refer to the same or similarcomponents. Components and modules can be implemented in software,hardware, or a combination of software and hardware. The term “software”is used expansively to include not only executable code, for examplemachine-executable or machine-interpretable instructions, but also datastructures, data stores and computing instructions stored in anysuitable electronic format, including firmware, and embedded software.The terms “information” and “data” are used expansively and includes awide variety of electronic information, including executable code;content such as text, video data, and audio data, among others; andvarious codes or flags. The terms “information,” “data,” and “content”are sometimes used interchangeably when permitted by context. It shouldbe noted that although for clarity and to aid in understanding someexamples discussed herein might describe specific features or functionsas part of a specific component or module, or as occurring at a specificlayer of a computing device (for example, a hardware layer, operatingsystem layer, or application layer), those features or functions can beimplemented as part of a different component or module or operated at adifferent layer of a communication protocol stack. Those of ordinaryskill in the art will recognize that the systems, apparatuses, devices,and methods described herein can be applied to, or easily modified foruse with, other types of equipment, can use other arrangements ofcomputing systems such as client-server distributed systems, and can useother protocols, or operate at other layers in communication protocolstacks, than are described.

Some of the figures can include a flow diagram. Although such figurescan include a particular logic flow, it can be appreciated that thelogic flow merely provides an exemplary implementation of the generalfunctionality. Further, the logic flow does not necessarily have to beexecuted in the order presented unless otherwise indicated. In addition,the logic flow can be implemented by a hardware element, a softwareelement executed by a computer, a firmware element embedded in hardware,or any combination thereof.

The foregoing description of embodiments and examples has been presentedfor purposes of illustration and description. It is not intended to beexhaustive or limiting to the forms described. Numerous modificationsare possible in light of the above teachings. Some of thosemodifications have been discussed, and others will be understood bythose skilled in the art. The embodiments were chosen and described inorder to best illustrate principles of various embodiments as are suitedto particular uses contemplated. The scope is, of course, not limited tothe examples set forth herein, but can be employed in any number ofapplications and equivalent devices by those of ordinary skill in theart. Rather it is hereby intended the scope of the invention to bedefined by the claims appended hereto.

1-22. (canceled)
 23. A method for enhancing credit transactions, themethod comprising: receiving, by a point of sale computing system,payment vehicle data for a credit transaction associated with a purchaseevent, the payment vehicle data corresponding to a payment vehicletendered for the credit transaction; detecting, based on payment vehicledata or a transaction-specific parameter, that the credit transaction isan alternate routing candidate; transmitting, by the point of salecomputing system, an authorization request message to an issuercomputing system via a private network, and receiving, by the point ofsale computing system, the authorization response message from theissuer computing system via a private network, or detecting, based onpayment vehicle data or a transaction-specific parameter, that that thecredit transaction is not an alternate routing candidate: transmitting,by the point of sale computing system, an authorization request messagefor the credit transaction to an issuer computing system via a secondnetwork out-of-band from the private network; and receiving, by thepoint of sale computing system, an authorization response message fromthe issuer computing system via the second network; and finalizing, bythe point of sale computing system, the credit transaction associatedwith the purchase event based on the authorization response message. 24.The method of claim 23, wherein the transaction-specific parametercomprises one or more of consumer data, loyalty data, offer data,account data, stock keeping unit (SKU) data, or a combination thereof.25. The method of claim 23, wherein the transaction-specific parameterincludes one or more of a bank identification number (BIN), an accountidentifier associated with the payment vehicle tendered for the credittransaction, a transaction interchange fee, or a combination thereof.26. The method of claim 23, wherein the second network does not transmitdata related to the transaction-specific parameter.
 27. The method ofclaim 23, wherein the private network comprises a personalidentification number (PIN) debit network.
 28. The method of claim 23,wherein the private network comprises a closed-loop communicationchannel connecting the point of sale computing system to the issuercomputing system, an acquirer computing system.
 29. The method of claim28, wherein the private network connects a plurality of point of salecomputing systems to a selected acquirer system, a selected issuercomputing system, or other selected computing device, or wherein theprivate network connects the point of sale computing system to aplurality of acquirer systems, a plurality of issuer systems, or aplurality of redemption platform operators, or wherein the privatenetwork connects a plurality of point of sale computing systems ordevices to a plurality of acquirer systems, a plurality of issuersystems, or a plurality of redemption platform operators.
 30. The methodof claim 23, wherein the second network comprises a card networkassociated with a payment vehicle.
 31. A system for enhanced credittransactions, the system comprising: a point of sale computing devicecomprising a processor executing instructions stored in memory, whereinthe instructions cause the processor to perform a method comprising:receiving, by a point of sale computing system, payment vehicle data fora credit transaction associated with a purchase event, the paymentvehicle data corresponding to a payment vehicle tendered for the credittransaction; detecting, based on payment vehicle data or atransaction-specific parameter, that the credit transaction is analternate routing candidate; transmitting, by the point of salecomputing system, an authorization request message to an issuercomputing system via a private network, and receiving, by the point ofsale computing system, the authorization response message from theissuer computing system via a private network, or detecting, based onpayment vehicle data or a transaction-specific parameter, that that thecredit transaction is not an alternate routing candidate: transmitting,by the point of sale computing system, an authorization request messagefor the credit transaction to an issuer computing system via a secondnetwork out-of-band from the private network; and receiving, by thepoint of sale computing system, an authorization response message fromthe issuer computing system via the second network; and finalizing, bythe point of sale computing system, the credit transaction associatedwith the purchase event based on the authorization response message. 32.The system of claim 31, wherein the transaction-specific parametercomprises one or more of consumer data, loyalty data, offer data,account data, stock keeping unit (SKU) data, or a combination thereof.33. The system of claim 31, wherein the transaction-specific parameterincludes one or more of a bank identification number (BIN), an accountidentifier associated with the payment vehicle tendered for the credittransaction, a transaction interchange fee, or a combination thereof.34. The system of claim 31, wherein the second network does not transmitdata related to the transaction-specific parameter.
 35. The system ofclaim 31, wherein the private network comprises a personalidentification number (PIN) debit network.
 36. The system of claim 31,wherein the private network comprises a closed-loop communicationchannel connecting the point of sale computing system to the issuercomputing system, an acquirer computing system.
 37. The system of claim36, wherein the private network connects a plurality of point of salecomputing systems to a selected acquirer system, a selected issuercomputing system, or other selected computing device, or wherein theprivate network connects the point of sale computing system to aplurality of acquirer systems, a plurality of issuer systems, or aplurality of redemption platform operators, or wherein the privatenetwork connects a plurality of point of sale computing systems ordevices to a plurality of acquirer systems, a plurality of issuersystems, or a plurality of redemption platform operators.
 38. The systemof claim 31, wherein the second network comprises a card networkassociated with a payment vehicle.
 39. A non-transitory computerreadable medium storing instructions that, when executed by a computer,cause the computer to perform a method comprising: receiving, by a pointof sale computing system, payment vehicle data for a credit transactionassociated with a purchase event, the payment vehicle data correspondingto a payment vehicle tendered for the credit transaction; detecting,based on payment vehicle data or a transaction-specific parameter, thatthe credit transaction is an alternate routing candidate; transmitting,by the point of sale computing system, an authorization request messageto an issuer computing system via a private network, and receiving, bythe point of sale computing system, the authorization response messagefrom the issuer computing system via a private network, or detecting,based on payment vehicle data or a transaction-specific parameter, thatthat the credit transaction is not an alternate routing candidate:transmitting, by the point of sale computing system, an authorizationrequest message for the credit transaction to an issuer computing systemvia a second network out-of-band from the private network; andreceiving, by the point of sale computing system, an authorizationresponse message from the issuer computing system via the secondnetwork; and finalizing, by the point of sale computing system, thecredit transaction associated with the purchase event based on theauthorization response message.
 40. The method of claim 39, wherein thetransaction-specific parameter comprises one or more of consumer data,loyalty data, offer data, account data, stock keeping unit (SKU) data,or a combination thereof.
 41. The method of claim 39, wherein thetransaction-specific parameter includes one or more of a bankidentification number (BIN), an account identifier associated with thepayment vehicle tendered for the credit transaction, a transactioninterchange fee, or a combination thereof.
 42. The method of claim 39,wherein the second network does not transmit data related to thetransaction-specific parameter.